Systems, methods and devices for convergent communications

ABSTRACT

Systems, devices and methods for convergence of a variety of communication sources are presented. More particularly, embodiments relate to a radio communications gateway device and associated methods, that is lightweight, small, portable, secure, and useful for converging communications via handheld radios to an internet protocol network having a variety of different available media. The device preferably has a weight under 15 pounds and sufficient interconnectability to be field-useful in a variety of situations.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a Continuation of U.S. application Ser. No.12/620,274, filed Nov. 17, 2009, incorporated herein by reference in itsentirety.

FIELD OF THE APPLICATION

The present application relates to the field of communications. Moreparticularly, the present application relates to systems, methods anddevices for converging a variety of communications media. Still moreparticularly, aspects of the present application relate to systems,methods and devices for integrating various types of communications withhighly portable radio communications. Still more specifically, certainaspects relate to the convergence of communications systems with radiocommunications suitable for use in remote areas or in difficult terrain,for example, communications for military operations. Devices of thepresent application include radio communications gateway devices asdescribed below.

SUMMARY

In one aspect of the present application, portable radios are able tocommunicate with a variety of communications media, such as analogtelephones or circuit-switched networks, Packet radio communicationsmedia IP networks, internet communications; TCP/IP networkcommunications; packet or frame-based networks using other protocols;serial (e.g., RS-232, USB) communications; satellite communications,etc. In the present application, the term “communications medium”implies a system for exchanging, providing or receiving information thatuses a known set of rules or protocols. There are a wide variety ofcommunications media possible.

A user of a portable or even handheld radio may be using the radiobecause of the user's surroundings. These surroundings may begeographically remote, without ready access to modern communications,unfamiliar, such that modern communications media can not be located oroperated, or insecure, such that existing modern communications are nottrustworthy. Users may also be operating in such a fashion that it isnot convenient to access modern communications.

There are, however, a wide variety of resources that could be useful tosuch users. Such resources include, but are not limited to, the abilityto speak or otherwise communicate with people or systems outside of therange of the radio system. Such resources are often provided overcommunications media that, for the foregoing reasons, are not easilyaccessible.

The inventors have thus perceived a need for a system that can be usedto integrate portable radio communications with other types ofcommunications. Because of the environment within which users of radiosmay be operating it is desirable that the system comprise a device thatis small, lightweight, portable, field-deployable and which has aminimum of external components, such as cables.

One specific embodiment relates to a radio communications gatewaydevice, comprising a housing having integrated connectors, theconnectors including at least two telephony port connectors, at leastone general-purpose serial port connector, at least four network portconnectors, and at least four radio interface port connectors; whereineach of the connectors is configured to facilitate communicationsignals; at least one processor; the at least one processor configuredto execute instructions recorded in a memory, such that a firstcommunications medium interfacing with one type of connector cancommunicate with a second communications medium interfacing with asecond type of connector; wherein the housing fits within one rack unit;and wherein the radio communications gateway device weighs less than 15pounds. Preferably, a height of a rack unit is 1.75 inches, and a widthis 23 inches or less, and still more preferably, a width of a rack unita width is 19 inches or less. Optionally, a depth of a rack unit is 40inches or less, and the device weighs less than 9 pounds.

In some embodiments, the integrated connectors include at least fourtelephony port connectors, at least two USB connectors, at least eightnetwork port connectors, at least four radio interface port connectors,and at least one console port connector. In others, the integratedconnectors include at least four telephony port connectors, at least twoUSB connectors, at least eight network port connectors, at least eightradio interface port connectors, and at least one console portconnector.

Optionally, the device further comprises a removable persistent storagedevice.

Preferably, the instructions comprise a LINUX-based operating system,and may further comprise at least two additional components insocket-based communication via a LINUX-based IP stack, a virtual machineconfigured to run a WINDOWS-based operating system, a management serverthat is configured to run on the WINDOWS-based operating system, a Webserver component configured to operate on the WINDOWS-based operatingsystem configured to run in the virtual machine, a Web server componentconfigured to operate on the LINUX-based operating system, wherein theWeb server configured to run on the LINUX-based operating system isfurther configured to provide a user interface that presents anabstraction of a radio control interface. Preferably, the Web serverconfigured to run on the LINUX-based operating system is furtherconfigured to communicate, via the LINUX-based operating system, with aradio control module that is configured to translate informationrelating to the abstraction of a radio control interface to therequirements of a specific radio control interface.

Optionally, the processor is provided on a board comprising a fixednumber of PCI slots and a fixed number of USB slots, and wherein aUSB-PCI emulator is connected to at least one of the USB slots.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a conceptual view of three levels of a system of a typeenvisioned for communication according to the present application.

FIG. 2 shows an example of basic communication in a system using threeconceptual levels as shown in FIG. 1.

FIG. 3 shows an example communications system.

FIG. 4 shows an example communications system.

FIG. 5 describes an implementation of a converged radio over internetprotocol (RoIP) network.

FIG. 6 illustrates a further application of the systems, methods anddevices of certain embodiments in an example communications system.

FIG. 7 illustrates yet another example communications system.

FIG. 8 a is a rear perspective view of an example radio communicationsgateway device.

FIG. 8 b is a front-face view of an example radio communications gatewaydevice.

FIG. 8 c is a rear face view of an example radio communications gatewaydevice.

FIG. 9 illustrates potential uses of radio interface gateway devices inan RoIP network.

FIG. 10 describes a possible interconnectional organization ofcomponents within a housing of a radio communications gateway device.

FIG. 11 describes an alternate possible interconnectional organizationof components within a housing of a radio communications gateway device.

FIG. 12 describes yet another an alternate possible interconnectionalorganization of components within a housing of a radio communicationsgateway device.

FIG. 13 depicts a possible software/hardware architecture of a radiocommunications gateway device.

FIG. 14 illustrates a digital voice segment.

FIG. 15 is a flow diagram showing administrative communication by a userthrough an example radio communications gateway interface.

FIG. 16 illustrates a circuit diagram for a hybrid audio conversion andamplification block according to one embodiment.

FIG. 17 is a block diagram of a radio-telephony interface boardaccording to one embodiment.

FIG. 18 shows an optoisolation circuit diagram according to anembodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The systems, methods and devices of the present invention comprisegenerally automated systems for radio communications, in particular, theconfluence of radio communications with packet-switched networks such asIP networks. Such systems, methods and devices are envisioned to becarried out on a computer system, which may comprise one or moreintegrated circuit or other processors that may be programmable orspecial-purpose devices. The system can comprise memory which may be oneor more devices, which may be persistent or non-persistent, such asdynamic or static random access memories, flash memories, electronicallyerasable programmable memories, or the like, having instructionsembedded therein, such that if executed by a programmable device, theinstructions will carry out methods as described herein to form systemsand devices having functions as described herein.

In the context of the present application, a “radio communicationsgateway device” means a device that facilitates the communication ofportable radio devices with other forms of communications.

A “housing” is a physical enclosure, which may be made of metal, plasticor the like, for one or more functional components. A “housing” may havea number of external access points, such as externally accessibleconnectors, switches, fasteners or access ports integrated into thehousing. The term “integrated,” when used to refer to physical objects,means that the objects are connected, and constructed to have theappearance of fitting together closely. When used to described concepts,“integrated” means “included in” or “part of” The term “connector” isused to mean a hardware plug, meant to match a corresponding hardwareplug to continue a connection.

A “telephony port” is a place to access a telephone circuit.

A “general-purpose serial port” is a place to access general purposeserial communications hardware. Examples of such communications caninclude USB (Universal Serial Bus), Firewire and RS-232, among others.In the context of the present application, the term “serial port” shouldnot be limited to RS-232 communications.

The term “network port” means a place to access packet-based networkcommunications, such as Ethernet or other LAN communications.

The term “radio interface port” means a place to access communicationswith a portable radio. Such communications can proceed using RS-232 orother protocols, but are designed to include a physical radio device asa communications partner.

The term “communication signals” generally means signals carried by amedium, such as the electromagnetic spectrum, whether over a wire,through the air, etc. Such communication signals by be interpreted asanalog or digital, may be packet or frame-based, may be multiplexed infrequency, time, code or the like, and may include multiple levels ofcontrol information.

The term “interface,” when used as a verb, means to exchangecommunications in an agreed-upon manner, or to physically matchcomponents in an agreed-upon manner.

The term “rack unit” means a physical storage unit size that hasrecognized standard dimensions, although more than one set of dimensionsis possible (i.e., there may be more than one standard).

FIG. 1 shows a conceptual view of three levels of a system 100 of a typeenvisioned for communication according to the present application.System 100 is represented by conceptual layers 102, 104 and 106. Varioususers of the system 100 will preferably have access to differentfacilities within the system that are grouped into conceptual layers,depending on the responsibilities of the particular users. For example,standard communications users may only need access to a few aspects ofthe system, whereas administrative users and technicians may need accessto more of the system, or the entire system. Various conceptual layersand protocols are used to separate data useful to converge differentcommunications media types.

Conceptual layer 106 reflects the physical communications media of thesystem, together with communication protocols used by those media, whichare largely transparent to communications users of the system, but canbe made accessible to administrative users of the system.

Conceptual layer 104 is an administrative layer, which depends onprotocols used in the physical communications media layer 106. Theadministrative layer 104 comprises facilities for managing lists ofusers and access privileges, security, software updates and otheradministrative activities.

Conceptual layer 102 represents various forms of communication data thatcan be carried by the system. Users able to access conceptual layer 102can use the system to communicate with one another.

In a packet-based embodiment, the order stacking of layers 102, 104 and106 can represent the order in which information is transmitted. Forexample, communications data (layer 102) can comprise voice data. Aone-minute recording of someone's voice can be broken up into numeroussmaller segments, represented digitally. An example is shown in FIG. 14.

FIG. 14 illustrates a digital voice segment 1402. Within the conceptuallayer 102 of FIG. 1, too this segment of data 1402, information 1404 and1406 can optionally be added. Information 1404 can be, for example,control information that indicates where in the entire one-minuterecording this particular segment of voice data occurs. Information 1404can be, for example error correction data if the transmission isparticularly noisy and high-quality is required.

Within the conceptual layer 104 of FIG. 1, further data 1408 and 1410 ofFIG. 14 can optionally be added. Data 1408 might be security-relateddata, for example, data related to transmission encryption oraccess-related data, for example, relating to a particular set of userswho are allowed to access data.

Within conceptual layer 106 of FIG. 1, data 1410, 1412 and 1414 canoptionally be added. Data 1410 can reflect information used by variouscommunications protocols, such as UDP or TCP and IP. Data 1412 canoptionally be data related to a lower-level physical protocol, such asframing data.

FIG. 2 shows an example of basic communication in a system 200 employingat least two nodes (locations with equipment) 202 and 204, having theconceptual layer model of FIG. 1. The two nodes 202 and 204 are incommunication 206 with one another at each conceptual level. At the toplevel, each node advertises through an advertising interface connectionsor streams to media sources, such as radios, telephones, video cameras,etc. At the middle level, each node communicates information regardingsecurity, access, and administrative privileges. At the bottom level,each node uses the protocols required by any medium that facilitatescommunication 206. Communication between nodes is preferablypeer-to-peer.

FIGS. 3-9 illustrate various aspects of using the systems, devices andmethods of the present application. Although these illustrations ofFIGS. 3-9 primarily illustrate military applications, the embodimentsare not limited to such applications, and can be useful in a variety ofsituations. Various embodiments can be useful in principle in any typeof communications system that employs multiple types of communication,particularly where at least one type of communication is intended to beemployed in a remote location or insecure environment, for example, forfield operations personnel of a geographic survey company, for police,for firefighters, for medical personnel, etc.

FIG. 3 shows a system 300 of the type shown in FIG. 2, having conceptuallayers as shown in FIG. 1, as it can be implemented. System 300 hasgovernment agency users 302 and 304, headquarters users 306 and 308, aninternet protocol wide-area network 316 (IP WAN), a forward operationsbase (FOB) user 310 and a joint special operations task force(JSOTF)/joint task force (JTF) user 312.

A collection of users, such as those shown in system 300, previously hada variety of different communications systems to use, and communicatedin disparate ways. According to system 300, each user has access to aconverged network of communications media. Although some users of system300 may only have access to limited and specific forms of communication(such as handheld radios provided by a variety of different vendors),these limited and specific forms of communication are converged onto anetwork using gateway devices and methods according to the presentapplication. This allows, in effect, headquarters users with stablelocations and access to more powerful computing equipment, will havebetter control over and access to disparate forms of communications inthe field.

In the system of FIG. 3, for example, command, administrative andtechnician users at headquarters (represented by users 306 and 308),have the ability to access media in the top conceptual layer, which mayconsist of audio from a variety different radio types and telephones inthe field, video from surveillance units, remote controlled-drones andstatic cameras, and other sources. Users 306 and 308 also have theability to control access privileges and security as necessary, and toreconfigure devices remotely.

External government agency users 302 and 304 may also need access tocertain types of media, without needing access to all privilegesassociated with the communications network. Agencies 302 and 304 can,then, be provided access over a network to selected portions of the topconceptual layer.

Users 310 and 312 represent base location users in the field. Theseusers have locations that are secure enough to have more extensivecommunications facilities. The base location users 310 and 312 can beconnected to headquarters users over an internet protocol (IP) wide-areanetwork (WAN) 316, that may operate by satellite, for example, to avoidthe use of physical communication lines.

FIG. 4 expands on the system of FIG. 3, where reference number 402corresponds to reference number 302 in FIG. 3, 404 to 304, 406 to 306,408 to 308, 410 to 310, 412 to 312 and 416 to 316. FIG. 4 also showsthat the FOB and JSOTF/JTF have radio transceivers 416 and 418, that arein communication 420 via High Frequency (HF) radio, Ultra-High Frequency(UHF) radio, Very High Frequency (VHF) radio, the TACSAT system ofsatellite communications, or other suitable means, with tactical teams422, 424 and 426. Communications with tactical teams 424 and 426 canoccur via team 422, which has a vehicle capable of carrying moreequipment and a longer range radio.

The system of FIG. 4 preferably has a radio over internet protocol(RoIP) capability. The radio communications are preferably converged toIP communications at the vehicle of tactical team 422, but can inprinciple be converged at any point in the network, including FOB 412 orJSOTF/JTF 414. The convergence of radio to IP allows, for example, usersat headquarters 406 and/or 408, or users at government agencies 402and/or 404, although they may be located far from tactical teams 424 and426, to speak with those tactical teams through handheld radios carriedby the teams. By using RoIP, for example, a user with an IP telephone atgovernment agency 404 can have a telephone call packetized and routed tovehicle 420, where a RoIP gateway device facilitates local communicationwith portable radios held by tactical teams 424 and 426.

The application layer protocol for RoIP communications with other userson the system is preferably similar to Session Initiation Protocol(SIP), as explained in RFC 3261, the contents of which are herebyincorporated by reference.

FIG. 5 describes an implementation of a converged RoIP network. Fig.shows various stations 502, 510, 518 and 538, each preferably havingrespective servers 508, 516, 520 and 542 for voice communications, emailcommunications and file communications, wherein a server can be hardwareand software, software, or a component of software. FIG. 5 also showsvarious field users 532 and 536, having portable radios 530 and 534.Personnel 504, 506, 512, 514, 522, and 540 at stations 502, 510, 518 and538, and personnel 528 and 544 at locations remote from stations 502,510, 518 and 538, are potentially in need of voice communications withfield radio users 536 and 532.

Field radio users 536 and 532 are in communication via radios 534 and530 with radios 524 and 522, respectively, which are radios of differenttypes. These radio communications can be converged to an IP network at aradio communications gateway device 523, or at a similar device locatedproximate to users 636 and 630. Once converged to an IP network, radiocommunications can be made accessible to voice media users 522, 528,514, 512, 504, 506, 540 and 544, via a number of intermediatecommunications media, which can include satellites communications (e.g.,526) or the public-switched telephone network (PSTN) 546.

FIG. 6 illustrates a further application of the systems, methods anddevices of certain embodiments. FIG. 6 shows again several stations 602,608, 624 and 620, each having respective servers 604, 612, 616 and 621as described in relation to FIG. 5. As with FIG. 5, field users 636 and630 use handheld radios 634 and 632 to communication with FOB radios 628and 626, respectively, which communications are converged to an IPnetwork at radio communications gateway device 623, or at devicesproximate to users 636 and 630.

These users in FIG. 6 further have access to display devices, such asportable computers, that allow them to receive data messages, such asemails and files via their handheld radios. Such communication can takeplace, for example, via the Personal Digital Assistant (PDA) standards184A or 188, which allow a display device such as a field-ready laptopto communicate (e.g., via a serial interface) with a portable radiocompliant with the standard.

Data messages are sent via radio over IP to radio communications gatewaydevices located near the users, and then communicated to the user'sdisplay devices from the radio communications gateway devices. Thisallows not only voice communications over a communications channel thatincludes a portable radio, but also facilitates the exchange of relevantdata. For example, a headquarters user may wish to speak directly with afield radio user, and at the same time send that user a new graphicsfile having updated map data.

FIG. 7 illustrates yet another aspect. FIG. 7 shows stations 700, 706,710 and 712, having servers 704, 708, 712 and 716 respectively, as wellas various users 702, 714 and 715. FIG. 7 also shows field users 736 and732, having portable radios 734 and 730 respectively, in communicationwith radios 720 and 718 respectively.

The various users 702, 714 and 715 have access privileges that allowthem to configure portable radios 720 and 718, and optionally 734 and730. This allows, for example, the users 702, 714 and/or 715 to change aradio's channel or security settings or to install or reconfiguresoftware on the radio, etc. Network policies, for example, can provideaccess control and security for radio configuration.

FIG. 8 a is a rear perspective view of an example radio communicationsgateway device 800. Device 800 has a housing 802, which can be metal,plastic, or any material suitable for field use. The housing ispreferably closed, and of one or more pieces joined to form a single boxunit. Housing 802 has a front face 804, a back face 806, length edge808, a height edge 810, and a depth edge 812. The dimensions of thehousing preferable fit within on rack unit. The length edge is 23 inchesor less, and more preferably 19 inches or less, the height edge 810 ispreferably 1.75 inches or less, but can optionally be two rack unitshigh, for example, 3.5 inches or less, and the depth edge 812 ispreferably 40 inches or less and more preferably 15 inches or less, andoptionally 10 inches or less.

Front face 804 is detailed in FIG. 8 b. FIG. 8 b shows a number ofcomponents and connectors that are preferably part of the radiocommunications gateway device and integrated into its housing. Component814 is the front panel of a removable storage medium device, such as aflash drive. The quick removability of the device allows for quicksecuring of the radio communications gateway device should theenvironment become insecure, or should the operator need to leave thedevice unattended. Optionally, the storage medium can also be encrypted.

Component 816 is preferably a dual universal serial bus (USB) port,having two USB connectors. Component 818 is preferably a console port,preferably of type RJ45. Component 820 preferably comprises eight 10/100Ethernet switch connectors. Component 822 is preferably a device powerswitch.

FIG. 8 c details the rear face 806 of housing 802. Rear face 806 hascomponent 824, which is preferably a set of four telephony connectors oftype RJ11. Component 826 is preferably a device identifier, such as anencoded label. Component 828 is preferably a set of eight serialinterface connectors, preferably DB-9 radio interface ports of femaletype. These connectors 828 may typically be used to interface to anumber of radios at a forward command site, which radios in turn may beused for different purposes, such as communicating with teams in thefield, communicating with a satellite communications system, orcommunicating with other bases or centers using line of sight or ad hocnetworks.

Component 830 is preferably a power connector, for example a NationalElectrical Manufacturers Association compliant connector, or otherconnector suitable for local requirements, such as the InternationalElectrotechnical Commission (IEC) 320-C16. The connector is preferablysupplies an internal power supply rated at 10 Amps/250 AC volts.

The device 800 preferably has a weight under 10 pounds, and morepreferably approximately 9.2 pounds or 8.8 pounds, where “approximately”means+/−0.25 pounds in this particular instance.

FIG. 9 illustrates potential uses of radio interface gateway devices inan RoIP network. FIG. 9 shows a number of wireless networks, such asad-hoc or mesh networks 902, 920, 946, or satellite network 948. FIG. 9also shows a number of different units in communications, for example, atactical operations center (TOC) 906, a vehicle unit 922 having avehicle 924, a vehicle unit 934 having a vehicle 944, personnel units950 and 958 having personnel 952 and 960 respectively, and a remote unit918.

Personnel unit 950 has an associated radio 953 and laptop 954. Personnelunit 958 also has an associated radio 964, which is connected with alaptop 962 computer via the radio's serial interface.

TOC 906 has an internal local area network (LAN) 908, which may be anEthernet network, which has a server 912, a laptop computer 914, a radiocommunications gateway device 910, and a radio 916. The radiocommunications gateway device 910 converges communications via radio 916onto a network, in this case TOC LAN 908. The radio 916 can beconnected, for example, to the radio communications gateway device viaone of several serial interface connectors 828 (with reference to FIG.8), while TOC LAN 908 can be connected to one of several Ethernetconnectors 820.

With reference again to FIG. 9, vehicles 922 and 934 have vehicle LANs928 and 938, respectively, laptop computers 930 and 940, respectively,and radio communications gateway devices 928 and 938 respectively, whichconverge communications via radios 932 and 942 onto the respectivevehicle LANs. The vehicles 922 and 934 also communicate with network 902via a radio link. Vehicle 922 has a radio 932 in communication withVoice Net 946, while vehicle 934 has a radio 942 in communication withsatellite network 948.

The convergence of radio communications via radio communications gatewaydevices 910, 928 and 938 allows for various users of the network toroute voice and non-voice media to various users of the network,including remote users 958, 950 and remote radio 918 seamlessly. Forexample, it is possible for the a user having access to network 902, touse a standard telephone and, entering proper codes, access radiocommunications gateway device 938 on vehicle 944, and use the device 938to operate radio 942 to speak with field unit 958 via radio 964.

As described in FIG. 8, the radio communications gateway devicesoptionally and preferably have a variety of connectors, that can be usedin addition to those mentioned above. For example, it is preferablypossible to plug in a variety of Ethernet cables, or other devices viaUSB or serial ports. Additional radios can be connected through serialports, and analog telephones via telephony ports such as RJ11, etc.

FIG. 10 describes a possible interconnectional organization ofcomponents within housing 20 of the radio communications gateway deviceof FIG. 8. This is one of several suggested organizations suggested forlimiting size the dimensions described with respect to FIG. 8.

FIG. 10 shows an organization of a radio communications gateway device1000, connected to an IP network 1002, a radio network 1004, at leastone radio via interfaces 1036, 1038 and 1040, a PSTN network 1042 and ananalog plain-old telephone service (POTS) compatible device 1044. Thelatter reference numerals are depicted as clouds in FIG. 10 to indicatethat their configurations may be highly variable—in principle, thesedevices and systems need only satisfy certain protocol.

In general, the lower side of FIG. 10 represents the rear of device 800of FIG. 8, while the upper side of FIG. 10 represents the front ofdevice 800, although the placement of individual components can vary.

Organization 1000 has a processor 1006, which in the drawing is shown asa single board, and which can include one or multiple integratedcircuits, for example. The processor 1006 is in communication with aflash drive 1008, a network interface 1010 such as a 10/100 Ethernetswitch with corresponding connectors, console port 1012 and USB ports1014. Processor 1006 is also in communication with a Voice InterfaceCard 1020 over a Peripheral Component Interconnect (PCI) bus. Voiceinterface card 1020 has, in the example of FIG. 10, four daughter cardslots 1022, which are occupied by one two-port foreign exchangesubscriber (FXS) card for providing appropriate connectors and PSTNservices to a connected analog telephone devices, and three two-portforeign exchange office (FXO) cards 1026, 1028 and 1030. FXO card 1026provides two connectors for receiving incoming connections from PSTNnetwork equipment. Boards 1024, 1026, 1028 and 1030 are of typescommercially available.

FXO cards 1028 and 1030 provide two connectors each, which are connectedin the organization of FIG. 10 to a Radio Interface Board, which ispreferably a small footprint printed circuit board. The purpose of theradio interface board is to provide impedance matching, voltage supply,signal manipulation and signal isolation between the radios and analogtelephones attached to the radio communications gateway device.

Processor 1006 is also connected in FIG. 10 over a USB connection to aDigital I/O card 1018 and over another USB connection to a SerialInterface Card 1016. Cards 1018 and 1016 are of types that arecommercially available. Cards 1032, 1018 and 1016 are then mapped toradio interface cable 1034, to carry out various radio functions, suchas device control, push-to-talk (PTT) and voice capabilities.

The USB connection can, in a preferred embodiment, be used to emulate aPCI connection. In some cases, an available processor board may have alimited number of PCI slots, which can not be expanded withoutsignificant expense, engineering and/or footprint consumption. In such acase, a USB to PCI converter device can be used to emulate PCIcommunications with processor 1006.

FIG. 11 illustrates an alternate internal organization. The referencenumerals 1102 through 1142 correspond to the components 1002 through1042 having the same final two digits, respectively. FIG. 11, however,shows an expanded organization with a second voice interface cart 1146,having an additional number of slots 1148. In the organization of FIG.11, two such slots are occupied with two-port FXO cards 1150 and 1152,which are connected to a second radio interface Board to facilitateadditional radio—telephony interfacing.

FIG. 12 shows yet another possible organization 1200. The referencenumerals 1104 through 1154 (except for 1110) of FIG. 11 correspond tosimilar parts of FIG. 12, although not all parts of FIG. 12 have beencorrespondingly labeled. FIG. 12 shows additional components, such astwo-port FXO cards 1256 and 1258, which occupy two of the card slots1248, and which interface with Radio interface board 1260, to provideadditional radio interface capabilities. Furthermore, additional DigitalI/O and Serial Interface cards 1262 and 1264 respectively, are provided.

FIG. 13 depicts a possible software/hardware architecture of a radiocommunications gateway device, such as the one depicted in FIG. 8. FIG.13 shows the device connected to an IP Network 1302, such as theInternet or a private IP network. FIG. 13 further shows the deviceconnected to radio interfaces 1304, which allows access to a radio. Thesoftware components of FIG. 13 include a LINUX-based operating system,1308, a Microsoft WINDOWS-based virtual machine 1310 that runs withinthe LINUX operating system 1308, a Microsoft Internet Information Server1312 that runs within the virtual machine 1310, a media switchmanagement server 1314, a Web server 1318, a serial over IP component1316, a Web-based administration component 1322, Web-based radio controlsoftware 1324, media switch engine 1326, PBX software 1328, and aWeb-based user interface 1332.

The architecture of FIG. 13 uses a LINUX-based operating system 1308, inthis embodiment described as a LINUX operating system. The LINUXplatform provides the kernel, or lowest-level software interface tohardware. The LINUX platform also facilitates communication betweenvarious components shown in FIG. 13, which are not all able tocommunicate with one another natively. To solve this problem, eachcomponent's internet protocol functionality is used to communicate viathe LINUX IP stack using the loopback address and a further identifierappropriate for the target of the communication. Each of the componentscommunicating via this method opens a socket to a local bus, having theloopback address and a respective port number. The LINUX IP stackassociates each socket address with a target application (includingitself), and redirects packets to their intended destination. The LINUXIP stack is thus the hub in a hub and spoke architecture. Thisconvenient mechanism for communication assists in the minimization ofcommunication facilities.

LINUX operating system 1308 also supports software and hardware thatperform the digitization of incoming analog audio streams, and theirseparation into packets for communications on an IP network. Thesepackets are managed by media switch software 1326 and media switchmanagement server 1314. The media switch software 1326 and managementserver 1314 are, in this example, implemented through WAVE softwarecurrently available from Twisted Pair communications.

The management server 1314 is currently only available via Microsoft'sActive Serve Pages technology, which requires a Microsoft WINDOWS-basedplatform, while the media switch component 1326 is available on a LINUXplatform. Wave software requires a management server to be reachable. Amanagement server such as server 1314 is typically in a trusted andphysically secure environment. In the embodiment of FIG. 13, however,the management server 1314 is provided on a radio communications gatewaydevice, which may be in a field environment. The server is provided inthe radio communications gateway device in order to provide forpeer-to-peer communications with other nodes within a communicationsnetwork, as opposed to client-server or master-slave communications thatmight have unacceptably long delays over a network.

To avoid the use of a separate physical component running a separateoperating system, the media switch management server 1314 is executedusing Active Server Pages inside a Microsoft WINDOWS virtual machine,which in turn facilitates Microsoft Internet Information Server andallows Active Server Pages to function. This makes the need for aseparate machine running a WINDOWS platform unnecessary, and makessecurity and error-handling easier within the overall context of a LINUXplatform.

Administration functions are performed via a Web interface 1332. The Webinterface is facilitated by a Web server 1318, which is preferablyimplemented as an Apache Tomcat server. The Web interface provides notonly for configuration of the radio communications gateway device 1300,but also for components, for example radios, connected thereto.

This Web-to-radio functionality is performed using serial-over-IPcomponent 1316, which is a back-end communication tool that isconfigured to communicate with radios of various types over a serial orother interface. That is, serial over IP component 1316 contains logicthat carries out manufacturer specific control over a radio. Forexample, the protocol for issuing a command to change a radio channel,or to key a radio, may be different from manufacturer to manufacturer,or even different from device-to-device within the same manufacturer'sproduct line. Preferably, these device-specific controls are abstractedto standardized controls, which are provided to the user via aWeb-interface. The user sees only options relating to the changing of achannel for example, and does not see the specific protocol necessary tocarry this channel change out for any particular radio.

Thus, control over many different types of radios can be implemented asshown in FIG. 15. FIG. 15 is a flow diagram 1500 showing administrativecommunication by a user through the radio communications gatewayinterface 1300. Assuming an authenticated user with sufficient accessprivileges has been identified, the user is allowed to make a request toserver 1318 at step 1502. The request can, for example, be an hypertexttransport protocol (HTTP) or secure HTTP (HTTPS) request to listavailable radios to configure. At step 1504, the Web Server 1318receives the request, and identifies connected radios using a local datastructure, such as a database or file, or performs a query via theoperating system 1302 to identify connected radios.

At step 1506, the user receives a Web page listing available radios,which may be limited by the user's access privileges. The useridentifies a radio of interest, and communicates this to the Web server1318. At step 1508, the Web Server 1318 sends a Web page withstandardized controls. At step 1510, the user sends a Web request formedby using the standardized controls, requesting that an operation beperformed on a radio local to the radio communications gateway device.At step 1512, the Web server 1318 receives the request, and formulatesan internal request to a socket, that is directed via the LINUX IP stackat step 1514, in a manner described above. Component 1316 receives therequest via the LINUX IP stack at step 1516, and translates the abstractcommand to a command that can be understood by the target radio.Component 1316 then uses LINUX operating system 1514 to control ahardware serial interface to communicate with the target radio, usingthat radio's required protocol. At step 1518, component 1316 sends aconfirmation that the procedure has been carried out via the LINUX IPstack. The LINUX IP stack at step 1520 forwards the confirmation to Webserver 1318 at step 1522, which may update its internal data store andsend an updated Web page to the user.

One advantage of the above-outlined administrative mechanisms is thatcontrol over the radio during configuration is maintained local to theradio. This means that network latency will not affect configuration.For example, some radios may require request/response interaction forspecific commands to be carried out, and network latency can causetimeouts that prevent configuration. Using the organization of FIG. 13and the method of FIG. 15, this difficulty can be largely avoided.

FIG. 17 is a block diagram showing an example Radio Interface Board 1700that could correspond to, for example, board 1032 of FIG. 10. The board1700 has a plurality of telephone ports 1702, a plurality of radio ports1704, a power supply connector 1706, a Push-To-Talk (PTT) connector1708, a hybrid audio conversion and amplification block of circuits1710, a power supply block 1712, and a PTT Optoisolation block 1714. Thepurpose of the board 1700 is to interface one or more portable radiodevices with one or more telephony devices, and in particular, tointerface voltage, impedance, signal levels, and signal composition.

A typical portable radio may operate with single ended audio. The signalis carried by a potential function on a single conductor, measured as avoltage relative to ground, rather than relative to another potentialfunction. There is one conductor for transmitted signals and oneconductor for received signals. The standard telephone service, incontrast, uses a composite signal with typically four conductors.Transmitted data is conveyed by a pair of wires and received data isconveyed by a pair of wires.

FIG. 16 illustrates a circuit diagram corresponding to one interface,within the hybrid audio conversion and amplification block 1710 of FIG.17, between a radio device and a telephony device. The interface circuit1600 of FIG. 16 includes a radio connector circuit 1602 and a telephonyconnector circuit 1604, which in this example can be a PCI telephonyboard. The interface circuit 1600 uses a hybrid circuit to separatetransmit and receive data for the radio and combine the radio's databack into a composite signal for the telephony board. In this processthe high impedance from the telephony board is matched via a transformerto the usually lower impedance of the radio. The signals are thenapplied to a dual operational amplifier circuit that separates the twoaudio paths and amplifies the separate signals to compensate for loss inthe conversion process. This action culminates with two separate signalsthat were once one, corrected impedance and levels that are matched totheir corresponding interfaces. The service also includes a DC Loop forcontrol signaling. The DC portion of the signal is used to indicate callstatus (e.g., in progress″), off/on hook and ringing. The telephonyprotocol is dissimilar to radio protocol, and these two protocols callfor an interface to work together.

Signals transmitted by the connector circuit 1604 are matched inimpedance and isolated by transformer 1606. The signal then passesthrough an audio coupling capacitor 1608, which filters the signal, andis fed to the negative terminal of operational amplifier 1610. Theoperational amplifier 1610 amplifies the signal due to the trans-hybridloss in the impedance balancing network. Once the signal is amplified itis passed through another coupling capacitor 1612 and applied to theradio input of connector circuit 1602.

For information sent from the radio to the telephone, the receive audiofrom the radio is applied to pin 2 of operational amplifier 1616 via theaudio coupling capacitor 1618. The signal is amplified by operationalamplifier 1616 to compensate for the loss of the balancing network. Theamplified signal is applied to the impedance matching circuitincorporating transformer 1606, and then on the PCI telephony board.

The connector circuit 1604, when embodied as a PCI telephony board, isconfigured to expect a 12V DC applied to its input. The 12V DC is acontrol signal that indicates to the PCI telephony board that there is acall in progress. Thus, in the board 1600, a 12V DC supply is suppliedto the PCI telephony board 1604 by injecting it on pin 1 of board 1604.To protect the remainder of radio interface board 1600 from the +12V DC,capacitor 1618 blocks the DC voltage but passes the audio signal.

FIG. 18 shows an optoisolation circuit diagram 1800 for PTTfunctionality for connected radios, corresponding to block 1714 in FIG.17. The diagram 1800 has a PTT control interface 1802, PTT output wires1804, optical coupling circuits 1806 and 1808, and light emitting diodes1810, 1812, 1814 and 1816. The PTT control interface 1802 transmitssignals (received, e.g., from a processor that in turn has received aninstruction from another communications device) that indicate that thePTT of a radio should be engaged. Output signals 1804 comprise PTT(signal) and ground pairs, for up to four radios in this particularconfiguration.

When a PTT engage signal is received and placed on a PTT control line,it activates a corresponding one of light-emitting diodes 1810, 1812,1814 or 1816, and engages a respective optical coupling circuit 1806 or1808. Each of the optical coupling circuits 1806 and 1808 are embodiedas dual circuits, meaning that two independent optical couplings arepossible, and are preferably embodied as fast switching OPTOMOS TTLrelays. The optical coupling serves to switch PTT functionality inattached radios, but prevents current from flowing between the PTTinterface of the attached radios and the remaining circuitry, toprevent, e.g., current loops from building where the ostensible groundterminals are not at the same potential.

Although the foregoing is described in reference to specificembodiments, it is not intended to be limiting or disclaim subjectmatter. Rather, the invention as described herein is defined by thefollowing claims, and any that may be added through additionalapplications. The inventors intend no disclaimer or other limitation ofrights by the foregoing technical disclosure.

1. A radio communications gateway device, comprising: a housingcomprising a plurality of types of integrated connectors, the connectorsincluding at least two telephony port connectors, at least onegeneral-purpose serial port connector, at least four network portconnectors, and at least four radio interface port connectors; whereineach of the connectors is configured to facilitate communicationsignals; at least one processor; the at least one processor configuredto execute instructions recorded in a memory, such that a firstcommunications medium interfacing with one type of connector cancommunicate with a second communications medium interfacing with asecond type of connector; wherein the housing fits within one rack unit;and wherein the radio communications gateway device weighs less than 15pounds.
 2. The device of claim 1, wherein the housing fits within a rackunit having a height of about 1.75 inches and a width of about 19 inchesor less.
 3. The device of claim 1, wherein the housing fits within arack unit having a height of about 1.75 inches, a width of about 23inches or less, and a depth of about 40 inches or less.
 4. The device ofclaim 1, which weighs less than 9 pounds.
 5. The device of claim 2,wherein the connectors include at least four telephony port connectors,at least two USB connectors, at least eight network port connectors, atleast four radio interface port connectors, and at least one consoleport connector.
 6. The device of claim 2, wherein the connectors includeat least four telephony port connectors, at least two USB connectors, atleast eight network port connectors, at least eight radio interface portconnectors, and at least one console port connector.
 7. The device ofclaim 1, further comprising a removable persistent storage device. 8.The device of claim 2, wherein the instructions comprise a LINUX-basedoperating system.
 9. The device of claim 8, wherein the instructionsfurther comprise a virtual machine configured to run a WINDOWS-basedoperating system.
 10. The device of claim 9, wherein the instructionsfurther comprise a management server that is configured to run on aWINDOWS-based operating system.
 11. The device of claim 8, wherein theinstructions further comprise a Web server component configured tooperate on the LINUX-based operating system.
 12. The device of claim 9,wherein the instructions further comprise a Web server componentconfigured to operate on the WINDOWS-based operating system configuredto run in the virtual machine.
 13. The device of claim 11, wherein theWeb server configured to run on the LINUX-based operating system isfurther configured to provide a user interface that presents anabstraction of a radio control interface.
 14. The device of claim 13,wherein the Web server configured to run on the LINUX-based operatingsystem is further configured to communicate, via the LINUX-basedoperating system, with a radio control module that is configured totranslate information relating to the abstraction of a radio controlinterface to the requirements of a specific radio control interface. 15.The device of claim 8, wherein the instructions further comprise atleast two additional components in socket-based communication via aLINUX-based IP stack.
 16. The device of claim 1, further comprising aradio telephony interface comprising an impedance-matching circuit andan amplification circuit.
 17. A method of manufacturing a radiocommunications gateway device, comprising: providing a housingcomprising a plurality of types of integrated connectors, the connectorsincluding at least two telephony port connectors, at least onegeneral-purpose serial port connector, at least four network portconnectors, and at least four radio interface port connectors; whereineach of the connectors is configured to facilitate communicationsignals; providing at least one processor; the at least one processorconfigured to execute instructions recorded in a memory, such that afirst communications medium interfacing with one type of connector cancommunicate with a second communications medium interfacing with asecond type of connector; wherein the housing fits within one rack unit;and wherein the radio communications gateway device weighs less than 15pounds.
 18. The method of claim 17, wherein the housing fits within arack unit having a height of about 1.75 inches and a width of about 23inches or less.
 19. The method of claim 17, further comprising:providing a radio telephony interface comprising an impedance-matchingcircuit and an amplification circuit; wherein the radio telephonyinterface further comprises an isolation circuit for isolating a groundterminal configured to be attached to a radio.
 20. The method of claim17, wherein the housing fits within a rack unit having a height of about1.75 inches and a width of about 19 inches or less; and wherein theconnectors include at least four telephony port connectors, at least twoUSB connectors, at least eight network port connectors, at least fourradio interface port connectors, and at least one console portconnector.